-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated all pages with new header UI #1056
Updated all pages with new header UI #1056
Conversation
Signed-off-by: Amardeepsingh Siglani <[email protected]>
Signed-off-by: Amardeepsingh Siglani <[email protected]>
public/pages/Dashboard/components/DashboardEmptyPrompt/DashboardEmptyPrompt.js
Show resolved
Hide resolved
can we upload the video with new UX? Also, let's monitor E2E for this PR, I remember e2e was failing for earlier PRs for this plugin |
Looks like there's a compile error in the alerting backend artifiact.
@amsiglan could you paste the result of running the tests locally? If that passes, I think we can merge this PR while waiting for the alerting backend compiler issue to be fixed. |
Signed-off-by: Amardeepsingh Siglani <[email protected]>
…edundant code; updated tests Signed-off-by: Amardeepsingh Siglani <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me. Approving assuming someone with more context into the requirements for the header changes also signs off.
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/alerting-dashboards-plugin/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.x
# Create a new branch
git switch --create backport-1056-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 db4af39b4af10d25e8f691795a95eb1191ce1354
# Push it to GitHub
git push --set-upstream origin backport-1056-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.x Then, create a pull request where the |
* updated all pages with new header UI Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed UTs Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed cross cluster API; cypress workflow Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed data source logic on page load for view/edit monitor; removed redundant code; updated tests Signed-off-by: Amardeepsingh Siglani <[email protected]> --------- Signed-off-by: Amardeepsingh Siglani <[email protected]>
* updated all pages with new header UI * fixed UTs * fixed cross cluster API; cypress workflow * fixed data source logic on page load for view/edit monitor; removed redundant code; updated tests --------- Signed-off-by: Amardeepsingh Siglani <[email protected]>
core.chrome.navGroup.addNavLinksToGroup( | ||
DEFAULT_NAV_GROUPS['security-analytics'], | ||
navLinks | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alerting is not supposed to be added to security-analytics, can we raise a PR to revert?
* updated all pages with new header UI Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed UTs Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed cross cluster API; cypress workflow Signed-off-by: Amardeepsingh Siglani <[email protected]> * fixed data source logic on page load for view/edit monitor; removed redundant code; updated tests Signed-off-by: Amardeepsingh Siglani <[email protected]> --------- Signed-off-by: Amardeepsingh Siglani <[email protected]> Signed-off-by: AWSHurneyt <[email protected]>
Description
This PR updates the header for each page to match the new core experience
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.